Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Tailoring startup scripts

Typically, the installation procedure automatically tailors the startup scripts for the OpenEdge products you install. Tailoring involves setting each script’s environment variable to point to the directory where you installed the product referenced by the script. If the installation procedure is interrupted before the script tailoring is complete or if the normal installation procedure is not used, you might have to tailor the scripts manually.

Depending on the products you purchase and install, your OpenEdge installation provides the required scripts. Some of the OpenEdge startup scripts are shown in the following table:

adaptman	mpro	proadsv	prooidrv
aiaman	mssman	proaiw	proserve
asbman	nsman	proapw	proshut
bpro	odbman	probiw	prowdog
dbman	oraman	probrkr	wsaman
mbpro	pro	prooibrk	wtbman

Note: The scripts listed above are located in $DLC/bin.

If the automatic tailoring did not take place, you receive the following error message when you try to start your OpenEdge product:

module-name not found

The module-name is the OpenEdge module that the script is trying to start. For example, if the script is pro, the module name is _progres.

To tailor your startup scripts manually:

Use any text editor to edit the scripts.
Look for the following syntax:

env_variable=${env_variable-pathname}; export env_variable

Change the pathname to the full pathname of the directory where you installed your OpenEdge product. For example:

DLC=${DLC-/usr/grp/dlc};export DLC